docs: clarify when Three.js needs Metro aliases - #451
Open
huytdps13400 wants to merge 1 commit into
Open
Conversation
wcandillon
self-requested a review
August 25, 2026 10:17
wcandillon
requested changes
Aug 25, 2026
wcandillon
left a comment
wcandillon
left a comment
Owner
There was a problem hiding this comment.
My current read of the situation would be to:
- update the three.js fiber template
- do a three.js only template
- as a bonus we do a pure WebGPU template
am I reading this correctly?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
three/webgpuexport without custom Metro aliasesthreeimports, and React Three FiberFixes #408
Verification
yarn workspace react-native-webgpu buildyarn workspace docs tscyarn workspace docs lintyarn workspace docs build:docs(26 static pages generated)git diff --check